Summary

This removes cypress as a direct dependency of Rancher Shell.

fixes #17622

Occurred changes and/or fixed issues

• Remove cypress from shell dependencies

Technical notes summary

I don't see a need for cypress to be included as a runtime dependency of shell after reviewing the Dashboard repo. Any project that consumes @rancher/shell currently inherits cypress as a transitive runtime dependency, including projects that have no need for it. Consumers that require cypress or any other E2E test framework for their own test suite should declare it explicitly in their own devDependencies.

Areas or cases that should be tested

Existing e2e functions should still function as they did before.

CI gates should pass.

Areas which could experience regressions

Any consumers of shell that rely on cypress as a transitive dependency will need to declare cypress as their own dev dependency. One might argue that @rancher/cypress can be used instead¹.

Screenshot/Video

NA

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base